-
Notifications
You must be signed in to change notification settings - Fork 421
chore(multiple): localize powertools_dev env logic and warning #1570
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore(multiple): localize powertools_dev env logic and warning #1570
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I made two suggestions. I executed it locally and in Lambda and it worked as expected.
Please check if it make sense.
…EVENT_HANDLER_DEBUG
Co-authored-by: Leandro Damascena <[email protected]>
Codecov ReportBase: 99.73% // Head: 99.74% // Increases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## develop #1570 +/- ##
========================================
Coverage 99.73% 99.74%
========================================
Files 124 124
Lines 5731 5771 +40
Branches 653 656 +3
========================================
+ Hits 5716 5756 +40
Misses 8 8
Partials 7 7
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
addressed Leandro's comments and he's OOTO today.
Thanks a lot for the useful suggestions! |
Issue number: #1527
Documentation being updated in #1569
Summary
Changes
POWERTOOLS_DEV
to ease adopting in other utilities laterPOWERTOOLS_DEV
in Event HandlerUser experience
Checklist
If your change doesn't seem to apply, please leave them unchecked.
Is this a breaking change?
RFC issue number:
Checklist:
Acknowledgment
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.